Systems and methods for multi-device wireless SIM management

ABSTRACT

Devices, systems and methods are disclosed for automated multi-device, multi-persona wireless SIM management. A virtual SIM database associated with a user is maintained on the mobile service provider&#39;s network. Such a virtual SIM database contains multiple personas for that user. For each of the user devices they wish to use on the mobile service network, the user is furnished with one “stub” SIM to be installed on the user device, onto which may be loaded any one of the personas maintained by the virtual SIM database. Upon an event, a selected user device downloads a selected persona from the network and loads it onto its stub SIM, so that the selected device is now registered on the network with that persona.

This application is a continuation of U.S. patent application Ser. No.12/370,666, filed Feb. 13, 2009, now U.S. Pat. No. 8,275,415, thecontent of which is hereby incorporated by reference herein in itsentirety into this disclosure.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of telecommunications. Inparticular, the present invention relates to dynamic management of theSubscriber Identification Module (SIM) card on telecommunicationsdevices.

2. Background of the Invention

As mobile device technology matures, more and more users wish to usemultiple user devices, and multiple identities, to connect to theirmobile service network. For example, one user may prefer to use one userdevice at work, with one set of features, while using a different userdevice with a different set of features at home, all the whilemaintaining a single identity on the network. A user may additionallypresent multiple identities to the network. For example, a user at workmay use their “work” identity for making telephone calls related tobusiness and a “personal” identity for making personal telephone calls.This may be, for instance, to avoid billing their personal calls totheir office.

Such identities are called “personas.” Typically, on the mobile servicenetwork itself, such distinct personas correspond to distinctInternational Mobile Service Identity (IMSI) numbers for the differentpersonas of the user. In the most general case, a user may wish tomanage multiple personas on multiple user devices.

Use of multiple user devices and multiple personas presents challengesfor both users and service providers, as usually the subscriber'sidentity on the network is derived from information stored on aSubscriber Identification Module (SIM) card that must be physicallyloaded onto the user device. Traditionally, management of which personais active on which user device had to be handled manually by the user.The user selects the SIM card for the desired persona and loads it ontothe desired user device.

Such an approach presents several disadvantages. Considering the mostgeneral case of a user with multiple personas and multiple user devices,it can be burdensome for the user. Typically, the user has to remove thebattery, remove the unwanted SIM card from the selected user device, andinsert the desired SIM card, possibly with the use of a smallscrewdriver. Switching over in this manner may require access to a userdevice that the user does not even wish to use, if it contains thedesired SIM card. If the user has forgotten to bring the user devicewith them, then they're out of luck. If the user wants access toinformation stored on a SIM card, such as saved text messages or contactinformation, they need the SIM card to be physically present, even if itis not in use at the time. Such a procedure also involves a lot ofhandling of the delicate SIM cards, which can be harmed by the oils inskin. Finally, such an ad hoc method of switchover makes it difficultfor the user to implement more planned switchover schemes. For example,a user may wish to activate their “home” persona every day at 5:00o'clock pm when they get out of work.

More recently, new technologies, like “Dual SIM” telephones, have beenintroduced to address some of these issues. Such phones contain twoslots onto which can be loaded two SIM cards, which can be activesimultaneously. However, such a solution still presents disadvantages.Because such telephones require much more hardware than typical phones,they are expensive. For example, such telephones require a slot for eachSIM card, a transceiver for each SIM card, etc. Additionally, a userwith more than two personas still needs to physically switch out a SIMcard to use the third persona. Finally, such a solution doesn't addressthe issues involved with a user who wishes to use multiple user deviceswith their set of personas.

Thus, there is a need for methods, systems, and associated devices formulti-device and multi-persona SIM card management that improve on thedeficiencies of the current art.

SUMMARY OF THE INVENTION

The present invention discloses systems, methods, and associated deviceswhich provide for automated multi-device, multi-persona management ofsmart cards with identity information. Such smart cards include, forexample, SIM cards, and the examples within this disclosure have beenpresented in terms of SIM cards for sake of simplicity but the presentinvention is not limited to such and may be used for any type of smartcard containing identity information. A number of virtual SIMsassociated with a user are maintained on the mobile service provider'snetwork in a virtual SIM database. Each virtual SIM is related to adifferent persona for that user (thus, the terms “persona” and “virtualSIM” are used as synonyms in what follows). For each of the user devicesthe user wishes to use on the mobile service network, the user isfurnished with one “stub” SIM to be installed on the user device, ontowhich may be loaded any one of the personas maintained by the virtualSIM database. Upon an event, a selected user device receives a selectedpersona from the network and loads it onto its stub SIM, so that theselected device is now registered on the network with that persona. Sucha change in the persona loaded onto a stub SIM can be referred to as a“switchover”.

In one exemplary embodiment of the present invention, the mobile servicenetwork is furnished with a Multi-SIM/Multi-Device (MS/MD) managementserver and associated databases responsible for managing which userpersonas are currently active on which user devices. In this embodiment,the user uploads a plurality of SIM management rules to the MS/MDserver, which then implements any switchovers of personas on the stubSIMs as determined by the user's preferences as expressed in the SIMmanagement rules.

In another exemplary embodiment of the present invention, a localdevice, such as a personal computer, is furnished with a localMulti-SIM/Multi-Device management application which allows the user tocreate a plurality of SIM management rules. Via communication betweenthe user devices and the mobile service network, switchover of personason the stub SIMs is effected.

In a further exemplary embodiment of the present invention, theinvention is a system of remote management of a persona on a SIM card,including a MS/MD management server, a user device in communication withthe SIM card and the MS/MD management server, and a virtual SIM databasestoring a plurality of personas associated with the user device. Upon anevent, the MS/MD management server sends a selected persona from theplurality of personas from the virtual SIM database to the user device,which loads the persona to the stub SIM card.

In yet another exemplary embodiment of the present invention, theinvention is a method of remote management of a persona on a SIM card,including designation of a plurality of SIM management rules by a user,upon an event, transmission of a persona to a user device of the user,and registration of the user device on a mobile service network usingthe persona. The persona to be transmitted to the user device isselected according to the SIM management rules and the event.

In another exemplary embodiment of the present invention, the inventionis a wireless telecommunications device including a device processor, aSIM management algorithm running on the device processor, a SIM cardprocessor in communication with the device processor, a SIM card memoryin communication with the SIM card processor, and a transceiver incommunication with the device processor. Upon an event, a persona istransmitted to the device processor via the transceiver, thereupon tothe SIM card processor, thereupon to the SIM card memory, all accordingto the SIM management algorithm.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B show a user's view of the capabilities of the presentinvention, according to an exemplary embodiment of the presentinvention.

FIG. 2 shows a user device with a stub SIM, according to an exemplaryembodiment of the present invention.

FIG. 3 shows a virtual SIM database maintained on a mobile servicenetwork, according to an exemplary embodiment of the present invention.

FIG. 4 shows a transfer of persona from a virtual SIM database to a userdevice, according to an exemplary embodiment of the present invention.

FIG. 5 shows network-based SIM provisioning, according to an exemplaryembodiment of the present invention.

FIG. 6 shows user preferences for SIM management rules for network-basedSIM provisioning, according to an exemplary embodiment of the presentinvention.

FIG. 7 shows local SIM provisioning, according to an exemplaryembodiment of the present invention.

FIG. 8 shows user preferences for SIM management rules for local SIMprovisioning, according to an exemplary embodiment of the presentinvention.

FIG. 9 shows a flow of information over a user device during SIMswitchover, according to an exemplary embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention discloses systems, methods, and devices whichprovide for automated multi-device, multi-persona management of smartcards with identity information. Such smart cards include but are notlimited to, for example, SIM cards. The examples within this disclosurehave been presented in terms of SIM cards for sake of simplicity but thepresent invention is not limited to such and may be used for any type ofsmart card containing identity information, as would be appreciated byone having ordinary skill in the art. A virtual SIM database associatedwith a user is maintained on the mobile service provider's network. Eachvirtual SIM in the virtual SIM database contains a different persona forthat user. This disclosure will use the term “persona” and “Virtual SIM”as synonyms in what follows. For each of the user devices the userwishes to use on the mobile service network, the user is furnished withone “stub” SIM to be installed on the user device, onto which may beloaded any one of the personas maintained by the virtual SIM database.Upon an event, a selected user device downloads a selected persona fromthe network and loads it onto its stub SIM, so that the selected deviceis now registered on the network with that persona. Such a change in thepersona loaded onto a stub SIM can be referred to as a “switchover”.

As used herein and throughout this disclosure, a “mobile servicenetwork” refers to any automated telecommunications network which allowsusers to connect to the network other than through a purely “hard-wired”connection, i.e., other than one in which the user's device has aphysical connection to the network. For example, the mobile servicenetwork may be a cellular RF network connecting mobile phones using anyappropriate communications standard (UMTS, GSM, IS-136, etc) andassociated communications technologies.

As used herein and throughout this disclosure, a “SIM card” refers toany integrated circuit card containing user identity information withwhich the user's device registers on the mobile service network.Associated with such a SIM card is a “persona”, which refers to the useridentity registered on the network with that SIM card. As should benoted, the examples presented in this disclosure are not limited to SIMcards per se and may be applicable to any type of smart cart containingidentity information.

As used herein and throughout this disclosure, a “user device” refers toany device with which the user maintains a connection to the mobileservice network. Examples of user devices are smart phones, mobiletelephones, mobile telephones, laptops, personal computers, satellitephones, a network-connected television, a network-connected appliance,personal digital assistants, etc.

For purposes of this disclosure, de-activation of a persona on a userdevice is considered to be loading of a null persona onto the userdevice. All that is disclosed regarding transmission of a persona to auser device may apply to de-activation of a persona on a user device aswell.

For the following description, it can be assumed that mostcorrespondingly labeled structures across the figures (e.g., 132, 232and 332, etc.) possess the same characteristics and are subject to thesame structure and function. If there is a difference betweencorrespondingly labeled elements that is not pointed out, and thisdifference results in a non-corresponding structure or function of anelement for a particular embodiment, then that conflicting descriptiongiven for that particular embodiment shall govern.

FIGS. 1A and 1B display a user's view of the capabilities of the presentinvention, according to an exemplary embodiment of the presentinvention. Associated with a user of a mobile service network is aplurality of personas. Such personas are characterized on the mobileservice network by unique identification numbers. In one embodiment ofthe present invention, these identification numbers are IMSI numbers.Associated with each persona is a distinct set of usertelecommunications information, such as user contacts, saved textmessages, a billing account, etc. Additionally, associated with the useris a plurality of user devices, each of which contains a stub SIM ontowhich the user selectively loads one of the associated personas.

Often a user wishes to use multiple personas on the same device atdifferent times. For instance, the user wants to separate the billingfor personal calls and work calls, but wants to use the same device forboth.

In FIG. 1A, associated with the user are two personas, a “work” persona100 and a “personal” persona 101 for use on a single user device 120.The user switches between these two personas on device 120 as isdesired. For example, the user may have work persona 100 active duringnormal working hours and personal persona 101 active during non-workhours. This allows the user to separate work calls from personal calls,as well as maintain different contacts for each. The use of multiplepersonas on a single device may simplify billing, allow for differentringtones or ringback tones for work and personal calls, etc.

Often a user wishes to use a single persona but with multiple devices.For instance, the user may not need all the functions of his work phonewhen making personal calls. The user may wish his personal phone to be asimple cellular phone with large buttons that is easy to use. The user'swork phone may need to be a smart phone with many buttons andapplications necessary for work. The user can utilize the same personafor both of these devices and switch between the two. In FIG. 1B,associated with the user is a persona 102, here named “combined”, andtwo user devices 121 and 122. In this embodiment, the user has set up aSIM management rule whereby device 121 is loaded with the “combined”persona during business hours and device 122 is loaded with the“combined” persona during off hours. When the device is not within itshours of use, the stub SIM of each device is blank, the null persona.The systems, methods, and associated devices of the present inventionallow the user to wirelessly load any of their associated personas ontoany of their associated devices.

FIG. 2 is a view of the back of a user device 220 of the presentinvention, according to an exemplary embodiment of the presentinvention. Replacing the SIM card typically inserted into such a deviceis a “stub” SIM 230 onto which the mobile service network can wirelesslyload any persona associated with the user of user device 220. Ratherthan the user having to swap SIM cards in order to load a given personaon a given device, the persona is downloaded onto stub SIM 230 from themobile service network so stub SIM 230 can stay in place once it hasbeen installed by the user. Although the method of loading a personaonto stub SIM 230 is unique to the present invention, stub SIM 230 maybe otherwise identical to SIM cards that currently are known in the art.

A user may maintain multiple personas on a virtual SIM database storedwithin the network or on the user's device. The virtual SIM databasecontains information for each of the personas. The network downloads apersona to the user's device according to predetermined criteria.

FIG. 3 displays a virtual SIM database 310, maintained on the mobileservice network, associated with a user “Ed Jones”, according to anexemplary embodiment of the present invention. The virtual SIM databaseincludes two persona files 300 and 301 linked under a subscriber namefield 312. Persona file 300 is labeled “Work” and persona file 301 islabeled “Personal”. Each persona file includes a unique personaidentification number 302, here labeled “IMSI”; a plurality of usercontacts 304; a plurality of user preferences 306, here listed asspecific ringtones to be played by the subscribed user's device whenthat persona is active on a stub SIM; and a plurality of saved textmessages 308. Information stored in virtual SIM database 310 that theuser can edit on his user device will be referred to as “user entered”information in this disclosure. For personas 300 and 301, user contacts304 and user preferences 306 thus qualify as “user entered” information.In some embodiments, such a virtual SIM database is “synchronized” withthe persona active on the subscribed user's stub SIM in the sense thatwhen the user makes changes to any of the user-entered information, thevirtual SIM database is updated with those changes as well.

The provision of a virtual SIM database that links all of the subscribeduser's personas together presents advantages for the user. For example,integration of the different personas in a variety of ways becomespossible. In some embodiments of the present invention, when the virtualSIM database is synchronized with the stub SIM due to a change in userentered information, user entered information existing on a currentlyactive persona can optionally be added to other personas on the virtualSIM database as well. For example, if the subscribed user enters acontact to his “Work” persona, such a contact could be optionally addedto the “Personal” persona as well. In some embodiments of the presentinvention, when the virtual SIM database is synchronized with the stubSIM due to a change in user entered information, and such a change isnoted to be “in conflict” with user entered information on anotherpersona, an alert is generated that notifies the user of the conflict.In an embodiment where the personas contain appointment calendars, sucha conflict happens, for example, when the user enters an appointment ontheir “Work” calendar that conflicts with an appointment on their“Personal” calendar.

Applications of persona integration become possible that go beyondintegration of user-entered information. If the user device supportsmultiple connections to the mobile service network, it becomes possiblefor different personas to make use of different channels ofcommunication between the user device and the mobile service networksimultaneously due to their linkage in the virtual SIM database. Forexample, 3G mobile service networks support simultaneous voice and dataconnections. Only one persona can be loaded onto the stub SIM of theuser device at one time. However, in one embodiment of the presentinvention, the user has permission to “assign” any data transmissionover the mobile service network to any persona contained on the virtualSIM database of the persona currently active on the stub SIM. In thisembodiment, the persona active on the stub SIM of the user device isreferred to as the “active” persona and the persona that the user wishesto assign a data transmission to is referred to as the “assigned”persona. The data transmission the user wishes to assign is referred toas the “assigned” data transmission. For purposes of communicationbetween the mobile service network and the device, the assigned datatransmission is routed by the mobile service network using the personaidentification number (i.e., IMSI number) of the active persona.However, in those aspects of the mobile service network responsible foraccounting for data transmissions, such as a billing server, the datatransmission is accounted to the assigned persona. This enables the userto, for example, undertake a voice call while downloading a file,billing the voice call to one persona and the file download to another.Integration of the personas contained in the virtual SIM databaseenables novel uses of the mobile service network.

Implementation of the system of the current invention may requirechanges to a mobile service network. These changes allow the network to,for instance, store and maintain virtual SIM databases as well asdownload personas to user devices.

FIG. 4 displays a schematic diagram of novel elements of the mobileservice network involved in transmitting a specified persona to a stubSIM 430 of a user device 420 once a request to send that persona to userdevice 420 has been recognized by the mobile service network, accordingto an exemplary embodiment of the present invention. In someembodiments, such a request is generated within the network while inother embodiments such a request is received from the user device. Amulti-SIM/multi-device (MS/MD) management server 440 sends a request toan associated virtual SIM database 450 for the specified persona,identified by its persona identification number. Virtual SIM database450 passes the requested persona to MS/MD management server 440, whereit is passed to a mobile switching center (MSC) 460 for transmission touser device 420 via a base station 470. The transmission of thespecified persona to user device 420 takes place using any appropriatetransmission technology and associated protocols. This may includetransmission as a SMS text message, as packet-switched data using a GPRSconnection, over a 3G data channel, etc. Once the persona has beenreceived by user device 420 it is loaded onto stub SIM 430 of userdevice 420.

FIG. 5 displays a schematic diagram of how information flows over themobile service network in one system of SIM switchover known as “networkbased SIM provisioning”, according to an exemplary embodiment of thepresent invention. In this network-based SIM provisioning, a MS/MDmanagement server 540 runs a global SIM management application 545 thattracks all of the user-selected SIM management rules of the user of auser device 520 and thus all of the user/user device/stub SIM attributesassociated with those user-selected SIM management rules. Tracking allthe user/user device/stub SIM attributes associated with theuser-selected SIM management rules of the user of user device 520requires communication between user device 520 and MS/MD managementserver 540 via MSC 560 and a base station 570. In this embodiment, astub SIM 530 of user device 520 is identified on MS/MD management server540 by its associated Integrated Circuit Card ID (ICCID) number. In someembodiments, the user device attributes associated with theuser-selected SIM management rules include a present GPS location ofuser device 520 and whether or not user device 520 is functioning. Whenuser device 520 is first powered on, it registers on the network viacommunication with an authentication center 580, which is responsiblefor authenticating all stub SIMs making a connection to the mobileservice network and thereafter generates an encryption key to enable allcommunications between MSC 560 and stub SIM 530 to be encrypted in theusual manner (e.g., through generation of triplets and use of anappropriate encryption algorithm). For this purpose, associated withstub SIM 530 is a security code, such as a Ki, known also toauthentication center 580. Once stub SIM 530 has been authenticated byauthentication center 580, stub SIM 530 is registered on MS/MD server540, a Home Location Register (HLR) 590, and a Visitor Location Register(VLR) 595 using its ICCID and persona identification number, such as anIMSI, if it has one.

Upon an event, MS/MD management server 540 implements the transmissionof a specified persona from virtual SIM database 550 to stub SIM 530 ofuser device 520. The persona to be transmitted has been selected byMS/MD management server 540 based on the SIM management rules chosen bythe user. MS/MD management server 540 requests the specified personafrom virtual SIM database 550 and passes it to MSC 560 for transmissionto user device 520 for its stub SIM 530. MS/MD management server 540notifies HLR 590 and VLR 595 of the activation of stub SIM 530 with thespecified persona. Thereafter, periodically MS/MD management server 540verifies that stub SIM 530 of user device 520, HLR 590, and VLR 595 allagree on the persona loaded on stub SIM 530 to ensure that, forinstance, all phone calls to user device 520 are properly routed andbilled. Additionally, if the user has effected any changes in theuser-entered information stored on the stub SIM 530 since the lastperiodic verification, such as if the user added a contact to their listof contacts on their stub SIM, the equivalent persona stored in virtualSIM database 550 is updated. Such periodic verification is referred toas “heartbeat synchronization” between stub SIM 530, HLR 590, VLR 595,and virtual SIM database 550. Because HLR 590 is constantly updated asto which personas are currently active and which are not, the mobileservice network knows, for example, which calls to connect in real-timeand which calls to connect to a voice mail server.

Because the specified persona must be transmitted to a particular stubSIM 530, and not simply a particular user, in its communications withuser device 520, MSC 560 must track all user devices on the networkusing the ICCIDs of their associated stub SIMs and not only theirpersona identification numbers (IMSIs). In this embodiment, all userdevices register on the network when they are powered on and are trackedin VLR 595 by the ICCID of their associated stub SIMs and their personaidentification numbers (IMSIs). User device requests, such as changes toa SIM management rule, are first parsed by HLR 590, which keeps track ofall user subscriptions to ensure that the user has subscribed to therequested service. For example, that the user has or has not subscribedto the virtual SIM management service is noted in their profile on HLR590. In some embodiments where the user has signed up for pre-paid phoneservice, transmission of a specified persona to a specified device canbe blocked if MSC 560 determines, via a call to HLR 590, that theremaining amount of pre-paid minutes in the user's account attached tothe specified persona is below a threshold amount. In some embodiments,MSC 560 blocks transmission of the specified persona if it determinesthat user device 520 is currently in use on the network. For example,user device 520 may be in the midst of a voice call or datatransmission.

In further embodiments, such an event triggering switchover is userschedule based upon the current time/day of the week, the present GPSlocation of the user, the user demand, etc.

FIG. 6 displays a screenshot of a user device 620 in a mode allowing theuser to add, edit, or delete a SIM management rule on the global SIMmanagement application on the MS/MD management server, according to anexemplary embodiment of the present invention. In this embodiment, theuser enters this mode by generating a request to the MS/MD managementserver, which downloads a plurality of selectable SIM management rulesto user device 620. Selectable SIM management rules include “time/day ofweek”, “schedule”, “GPS location”, etc. The user uploads the desired SIMmanagement rule to the MS/MD management server via any suitabletelecommunications technology and associated protocols, such as GPRS,UMTS, etc. The MSC sends a request to the HLR to verify that the userhas subscribed to the virtual SIM database service, and if so, the newSIM management rule is loaded into the global SIM management applicationon the MS/MD management server.

FIG. 7 displays an alternative system of SIM switchover, “localprovisioning”, according to an exemplary embodiment of the presentinvention. In this embodiment, a user device 720 generates requests forSIM switchover to the mobile service network. A local MS/MD managementapplication 747 is downloaded from a MS/MD management server 740 to alocal device 724. Such a local device may be a personal computer,laptop, etc. A plurality of user inputs 797 to local device 724 are usedto set up a plurality of SIM management rules, which are thentransmitted to a SIM management application 749 of user device 720. Thetransmission may use any suitable means of communication between localdevice 724 and user device 720. In one embodiment, a “synchronization”link 799 using MICROSOFT Mobile Device Center software is used. Becausethe SIM management rules potentially contain personal information aboutthe user of user device 720, it is important that such synchronizationlink 799 is secure. Additionally, to ensure that the user does notincorporate an unauthorized SIM card into the SIM management rules, suchas a SIM card not authorized for use on the mobile service network, insome embodiments, the acceptable stub SIM ICCIDs are not entered by theuser but rather included in local MS/MD management application 747downloaded from MS/MD management server 740.

FIG. 8 displays a screenshot of a local device 824 showing a pluralityof SIM management rules 826 the user can select and tailor fordownloading personas to their stub SIMs, according to an exemplaryembodiment of the present invention. Selectable SIM management rules inthis embodiment include “time/day of week”, “date”, “GPS location”, etc.Selecting “time/day of week”, the user sets up their user devices forautomatic switchover of a selected persona to a selected stub SIM of auser device at a certain time of day on a certain day of the week.Selecting “date”, the user sets up automatic switchover of a selectedpersona to a selected stub SIM of a user device at a certain time on acertain date. Selecting “GPS location”, the user sets up automaticswitchover of a selected persona to a selected stub SIM of a user devicewhenever the user device is within a certain radius of a specified GPSlocation, such as the user's home. In some embodiments, an additionalSIM management rule able to be selected by the user transmits to thestub SIM of any user device that has just been powered on apre-determined persona and deactivates the personas resident on anyother stub SIMs of the user. Such a SIM management rule is especiallyuseful when there are multiple user devices associated with the user,but only one persona. In some embodiments, if the user is associatedwith multiple user devices in their virtual SIM database, an additionalSIM management rule, able to be selected by the user, transmits thepersona on the stub SIM of the currently active device to anotherinactive, but registered on the mobile service network, user device.This may occur in the event that the mobile service network detectscommunication failure between itself and the currently active userdevice. Communication failure could stem from a variety of factorsincluding a user device malfunction, a user device running out ofenergy, etc. Such a SIM management rule is referred to as “failover”.

FIG. 9 displays the flow of information over the user device duringswitchover, according to an exemplary embodiment of the presentinvention. This flow of information is directed by a SIM managementalgorithm 928 resident on a user device microprocessor 933. The newpersona is received at a transceiver 936 and is transferred via userdevice microprocessor 933 to a user device memory 937 while user devicemicroprocessor 933 enables a connection to a stub SIM microprocessor934. Communications between user device microprocessor 933 and stub SIMmicroprocessor 934 occur using any appropriate communication protocolsfor the stub SIM-user device interface. For example, the ISO-7816-4communication protocols may be implemented using any appropriate SIMtoolkit (STK) standard (GSM 11.11, GSM 11.14, etc.). Once stub SIMmicroprocessor 934 has notified user device microprocessor 933 that itis ready to accept the new persona, the persona is transferred from userdevice memory 937 to a stub SIM memory 938. In some embodiments, stubSIM memory 938 is EEPROM memory. Once the new persona has beensuccessfully stored in stub SIM memory 938, SIM management algorithm 928reboots user device microprocessor 933 and thereupon, the user device isregistered on the mobile service network with the new persona. Infurther embodiments, a message indicating that the new persona has beenreceived is displayed to the user via a user display 939 and the usermust approve of the switchover before the new persona is loaded onto thestub SIM by assenting via a plurality of user inputs 929.

The foregoing disclosure of the exemplary embodiments of the presentinvention has been presented for purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many variations andmodifications of the embodiments described herein will be apparent toone of ordinary skill in the art in light of the above disclosure. Thescope of the invention is to be defined only by the claims appendedhereto, and by their equivalents.

Further, in describing representative embodiments of the presentinvention, the specification may have presented the method and/orprocess of the present invention as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible. Therefore, the particular order of the steps set forth inthe specification should not be construed as limitations on the claims.In addition, the claims directed to the method and/or process of thepresent invention should not be limited to the performance of theirsteps in the order written, and one skilled in the art can readilyappreciate that the sequences may be varied and still remain within thespirit and scope of the present invention.

What is claimed is:
 1. A wireless communication device comprising: amemory; and a processor that, when executing an algorithm, causes thewireless communication device to perform operations comprising sending,to a management server, a request to select a persona associated withthe wireless communication device, the persona comprising one personaselected from a group of personas comprising a work persona and apersonal persona, receiving, from the management server, the persona,loading the persona to the memory, and registering with a network usingthe persona, wherein the persona is synchronized with one of the groupsof personas associated with the wireless communication device.
 2. Thewireless communication device of claim 1, wherein the algorithm, whenexecuted by the processor, causes the wireless communication device toperform operations further comprising: deactivating the persona; andactivating a pre-determined persona.
 3. The wireless communicationdevice of claim 2, wherein deactivating the persona comprises loading anull persona to the memory.
 4. The wireless communication device ofclaim 1, wherein the memory comprises a smartcard memory.
 5. Thewireless communication device of claim 4, wherein the smartcardcomprises a subscriber identity module.
 6. The wireless communicationdevice of claim 5, further comprising a further subscriber identitymodule, wherein the subscriber identity module stores the persona, andwherein the further subscriber identity module stores a pre-determinedpersona.
 7. The wireless communication device of claim 1, wherein abilling account is associated with the persona.
 8. A memory that storesan algorithm thereon that, when executed by a processor, causes theprocessor to perform operations comprising: sending, to a managementserver, a request to select a persona associated with a wirelesscommunication device, the persona comprising one persona selected from agroup of personas comprising a work persona and a personal persona;receiving, from the management server, the persona; loading the personato the memory; and registering with a network using the persona, whereinthe persona is synchronized with one of the groups of personasassociated with the wireless communication device.
 9. The memory ofclaim 8, wherein the algorithm, when executed by the processor, causesthe wireless communication device to perform operations furthercomprising: deactivating the persona; and activating a pre-determinedpersona.
 10. The memory of claim 9, wherein deactivating the personacomprises loading a null persona to the memory.
 11. The memory of claim8, wherein the work persona has a first unique associated identificationnumber, and wherein the personal persona has a second unique associatedidentification number.
 12. The memory of claim 8, wherein a billingaccount is associated with the persona.
 13. A method comprising:sending, by a wireless communication device comprising a processor andto a management server, a request to select a persona associated withthe wireless communication device, the persona comprising one personaselected from a group of personas comprising a work persona and apersonal persona; receiving, by the wireless communication device andfrom the management server, the persona, wherein the management serverselects the persona from a database that stores the groups of personascomprising the work persona and the personal persona; loading, by thewireless communication device, the persona to the memory; andregistering, by the wireless communication device, with a network usingthe persona, wherein the persona is synchronized with one of the groupsof personas associated with the wireless communication device.
 14. Themethod of claim 13, further comprising: deactivating, by the wirelesscommunication device, the persona; and activating, by the wirelesscommunication device, a pre-determined persona.
 15. The method of claim14, wherein deactivating the persona comprises loading, by the wirelesscommunication device, a null persona to a memory of the wirelesscommunication device.
 16. The method of claim 13, wherein the memorycomprises a smartcard memory.
 17. The method of claim 16, wherein thesmartcard comprises a subscriber identity module.
 18. The method ofclaim 17, wherein the subscriber identity module stores the persona, andwherein a further subscriber identity module of the wirelesscommunication device stores a pre-determined persona.
 19. The method ofclaim 13, wherein a billing account is associated with the persona.